Skip to main content

Explain in detail Work Breakdown Structure (WBS) with example.

Work Breakdown Structure (WBS): Definition and Purpose​

A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project by breaking down the work into smaller, more manageable components.

The WBS serves as a fundamental project management tool that:

  1. Defines Project Scope: Visually represents all the work that must be done
  2. Facilitates Planning: Provides a framework for detailed schedule development
  3. Supports Estimation: Enables more accurate cost and resource estimations
  4. Improves Control: Establishes a baseline for measuring progress
  5. Clarifies Responsibilities: Helps assign ownership for each work component

Key Characteristics of a WBS​

1. Hierarchical Structure​

The WBS is organized in a tree-like hierarchical structure with:

  • Level 1: The project title (top level)
  • Level 2: Major deliverables or phases
  • Level 3+: Progressive decomposition of deliverables into smaller components
  • Work Packages: The lowest level components that can be scheduled, cost estimated, monitored, and controlled

2. The 100% Rule​

The 100% rule is a core principle stating that the WBS includes 100% of the work defined by the project scope and captures all deliverables—internal, external, and interim—in terms of work to be completed.

3. Mutually Exclusive Elements​

Each WBS component at any level must represent work that is:

  • Distinct from other components (no overlap)
  • Clearly differentiated from other elements at the same level
  • Not duplicated elsewhere in the WBS

4. Focus on Deliverables​

A well-constructed WBS focuses on deliverables rather than actions. It represents what needs to be produced rather than how it will be produced.

5. Progressive Elaboration​

The WBS is developed through progressive elaboration, becoming more detailed as the project planning advances and more information becomes available.

Types of WBS Structures​

1. Deliverable-Oriented WBS​

Organizes work around the tangible or intangible project deliverables.

2. Phase-Based WBS​

Structures work according to the chronological phases of the project lifecycle.

3. Functional WBS​

Organizes work based on the functional departments or disciplines involved.

4. Hybrid WBS​

Combines elements of the above approaches to best suit the project's needs.

Creating a Work Breakdown Structure​

The process of creating a WBS typically involves the following steps:

1. Identify the Project Deliverables​

  • Review project scope statement, requirements documentation, and other project artifacts
  • Identify all major deliverables that must be produced
  • Consider organizational process assets and templates from similar projects

2. Decompose the Deliverables​

  • Break down each major deliverable into smaller, more manageable components
  • Continue decomposition until work packages reach an appropriate size (the "rule of thumb" suggests 8-80 hours of effort)
  • Ensure each component represents a clear deliverable or result

3. Structure the WBS​

  • Organize components in a logical hierarchy
  • Apply consistent naming conventions
  • Ensure all work is included (100% rule)
  • Verify there is no overlap between components

4. Assign Identification Codes​

  • Create a unique identification code for each WBS element
  • Use a numbering system that reflects the hierarchical structure
  • Facilitate referencing specific components throughout project documentation

5. Develop the WBS Dictionary​

  • Create detailed descriptions of each WBS component
  • Include information such as:
    • Scope description
    • Deliverables
    • Acceptance criteria
    • Resources required
    • Estimated costs and duration
    • Responsible parties

6. Verify Completeness​

  • Review the WBS with key stakeholders
  • Ensure nothing is missing and nothing is duplicated
  • Confirm that the lowest level represents appropriate work packages

WBS Example: Software Development Project​

Below is an example of a WBS for a software development project creating a customer relationship management (CRM) system:

1.0 CRM System Development Project
│
├── 1.1 Project Management
│   ├── 1.1.1 Project Planning
│   │   ├── 1.1.1.1 Project Charter
│   │   ├── 1.1.1.2 Project Schedule
│   │   └── 1.1.1.3 Resource Plan
│   │
│   ├── 1.1.2 Project Monitoring and Control
│   │   ├── 1.1.2.1 Status Reports
│   │   ├── 1.1.2.2 Team Meetings
│   │   └── 1.1.2.3 Risk Management
│   │
│   └── 1.1.3 Project Closure
│       ├── 1.1.3.1 Final Documentation
│       ├── 1.1.3.2 Lessons Learned
│       └── 1.1.3.3 Project Acceptance
│
├── 1.2 Requirements
│   ├── 1.2.1 Business Requirements
│   │   ├── 1.2.1.1 Stakeholder Interviews
│   │   ├── 1.2.1.2 Process Mapping
│   │   └── 1.2.1.3 Requirements Workshops
│   │
│   ├── 1.2.2 Functional Requirements
│   │   ├── 1.2.2.1 User Stories
│   │   ├── 1.2.2.2 Use Cases
│   │   └── 1.2.2.3 Functional Specifications
│   │
│   └── 1.2.3 Non-Functional Requirements
│       ├── 1.2.3.1 Performance Requirements
│       ├── 1.2.3.2 Security Requirements
│       └── 1.2.3.3 Usability Requirements
│
├── 1.3 Design
│   ├── 1.3.1 System Architecture
│   │   ├── 1.3.1.1 Architecture Diagram
│   │   ├── 1.3.1.2 Technology Stack Documentation
│   │   └── 1.3.1.3 Integration Framework
│   │
│   ├── 1.3.2 Database Design
│   │   ├── 1.3.2.1 Data Model
│   │   ├── 1.3.2.2 Entity Relationship Diagrams
│   │   └── 1.3.2.3 Data Dictionary
│   │
│   └── 1.3.3 UI/UX Design
│       ├── 1.3.3.1 Wireframes
│       ├── 1.3.3.2 UI Style Guide
│       └── 1.3.3.3 Prototype
│
├── 1.4 Development
│   ├── 1.4.1 Database Development
│   │   ├── 1.4.1.1 Schema Creation
│   │   ├── 1.4.1.2 Stored Procedures
│   │   └── 1.4.1.3 Data Migration Scripts
│   │
│   ├── 1.4.2 Backend Development
│   │   ├── 1.4.2.1 API Development
│   │   ├── 1.4.2.2 Business Logic Implementation
│   │   └── 1.4.2.3 Integration Services
│   │
│   └── 1.4.3 Frontend Development
│       ├── 1.4.3.1 UI Components
│       ├── 1.4.3.2 Form Validation
│       └── 1.4.3.3 Client-Side Integration
│
├── 1.5 Testing
│   ├── 1.5.1 Test Planning
│   │   ├── 1.5.1.1 Test Strategy
│   │   ├── 1.5.1.2 Test Plan
│   │   └── 1.5.1.3 Test Cases
│   │
│   ├── 1.5.2 Testing Execution
│   │   ├── 1.5.2.1 Unit Testing
│   │   ├── 1.5.2.2 Integration Testing
│   │   ├── 1.5.2.3 System Testing
│   │   └── 1.5.2.4 User Acceptance Testing
│   │
│   └── 1.5.3 Defect Management
│       ├── 1.5.3.1 Defect Tracking
│       ├── 1.5.3.2 Defect Resolution
│       └── 1.5.3.3 Regression Testing
│
├── 1.6 Deployment
│   ├── 1.6.1 Deployment Planning
│   │   ├── 1.6.1.1 Deployment Strategy
│   │   ├── 1.6.1.2 Rollback Plan
│   │   └── 1.6.1.3 Production Environment Setup
│   │
│   ├── 1.6.2 Data Migration
│   │   ├── 1.6.2.1 Data Extraction
│   │   ├── 1.6.2.2 Data Transformation
│   │   └── 1.6.2.3 Data Loading
│   │
│   └── 1.6.3 Go-Live
│       ├── 1.6.3.1 System Deployment
│       ├── 1.6.3.2 Post-Deployment Validation
│       └── 1.6.3.3 Production Support Handover
│
└── 1.7 Training and Documentation
    ├── 1.7.1 User Documentation
    │   ├── 1.7.1.1 User Manual
    │   ├── 1.7.1.2 Online Help System
    │   └── 1.7.1.3 Quick Reference Guides
    │
    ├── 1.7.2 Technical Documentation
    │   ├── 1.7.2.1 System Documentation
    │   ├── 1.7.2.2 API Documentation
    │   └── 1.7.2.3 Maintenance Guide
    │
    └── 1.7.3 Training
        ├── 1.7.3.1 Training Plan
        ├── 1.7.3.2 Training Materials
        └── 1.7.3.3 Training Sessions

Benefits of Using a WBS​

1. Project Planning Benefits​

  • Scope Clarity: Ensures all project work is identified and accounted for
  • Better Estimating: Provides a framework for more accurate cost and effort estimation
  • Resource Planning: Helps identify required skills and resources
  • Risk Identification: Facilitates identification of risks at the work package level

2. Project Execution Benefits​

  • Clear Responsibilities: Defines who is responsible for each work component
  • Improved Communication: Creates a common language for discussing project work
  • Progress Monitoring: Enables tracking progress against a defined baseline
  • Change Management: Provides a structured approach to assess the impact of changes

3. Project Control Benefits​

  • Performance Measurement: Supports earned value management techniques
  • Issue Management: Helps isolate and address problems at the work package level
  • Scope Management: Makes scope creep more visible and manageable
  • Integration Management: Facilitates coordination between different project areas

Practical Guidelines for Effective WBS Development​

1. Level of Detail​

  • Decompose to the level needed for effective management control
  • Ensure work packages are:
    • Manageable in size (typically 8-80 hours of effort)
    • Assignable to a single responsible person
    • Clearly defined with start and end points
    • Measurable for progress reporting

2. Naming Conventions​

  • Use nouns for deliverables and components
  • Be specific and descriptive
  • Use consistent terminology
  • Avoid vague terms

3. Coding Structure​

  • Use a consistent numbering system
  • Design codes to reflect the hierarchical structure
  • Consider integration with other organizational systems
  • Allow for future expansion

4. Visual Presentation​

  • Choose an appropriate format based on project needs:
    • Hierarchical tree diagram
    • Indented outline
    • Tabular format
    • Mind map

5. Common Pitfalls to Avoid​

  • Too Much Detail: Excessive decomposition can make the project unwieldy
  • Too Little Detail: Insufficient decomposition can lead to inadequate planning
  • Mixing Deliverables and Activities: Confusing what needs to be produced with how it will be produced
  • Incomplete Scope: Failing to include all project work
  • Overlapping Elements: Creating components with overlapping responsibilities

WBS Tools and Techniques​

Several tools and techniques can assist in WBS development:

1. Decomposition Techniques​

  • Top-down decomposition: Starting with the major deliverables and breaking them down
  • Bottom-up decomposition: Identifying detailed tasks and grouping them into larger components
  • Mind mapping: Using associative thought processes to identify and organize components

2. Templates and Historical Information​

  • WBS templates from similar past projects
  • Industry-specific templates
  • Organizational process assets

3. Software Tools​

  • Project management software (e.g., Microsoft Project, Primavera)
  • Mind mapping software (e.g., MindManager, XMind)
  • Specialized WBS tools (e.g., WBS Chart Pro)
  • Collaborative tools (e.g., Miro, Lucidchart)

The WBS and Other Project Management Elements​

The WBS serves as a foundation for many other project management elements:

1. Schedule Management​

  • Work packages form the basis for activity definition
  • WBS provides the framework for the project schedule
  • Helps identify dependencies between work elements

2. Cost Management​

  • Work packages are the level at which costs are estimated
  • Forms the basis for the cost breakdown structure
  • Supports budget allocation and cost control

3. Resource Management​

  • Helps identify required skills and expertise
  • Supports resource allocation planning
  • Facilitates responsibility assignment

4. Risk Management​

  • Provides a structured approach for risk identification
  • Helps assess risk impacts at the work package level
  • Supports development of risk response strategies

5. Quality Management​

  • Defines the components that require quality control
  • Supports development of quality metrics
  • Facilitates quality assurance planning

Conclusion​

The Work Breakdown Structure is a fundamental project management tool that provides a comprehensive framework for defining and organizing project work. By systematically decomposing the project scope into manageable components, the WBS enables effective planning, estimating, and control throughout the project lifecycle.

A well-developed WBS serves as the backbone for project execution, helping ensure that all work is identified, assigned, and completed according to plan. It provides a common reference point for all project stakeholders and supports communication, coordination, and decision-making throughout the project.

When created with appropriate detail and maintained throughout the project, the WBS significantly increases the likelihood of project success by providing clarity, focus, and structure to the complex endeavor of project management.